-
Notifications
You must be signed in to change notification settings - Fork 800
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Protect: React Query #39036
Protect: React Query #39036
Conversation
Thank you for your PR! When contributing to Jetpack, we have a few suggestions that can help us test and review your patch:
This comment will be updated as you work on your PR and make changes. If you think that some of those checks are not needed for your PR, please explain why you think so. Thanks for cooperation 🤖 The e2e test report can be found here. Please note that it can take a few minutes after the e2e tests checks are complete for the report to be available. Follow this PR Review Process:
Still unsure? Reach out in #jetpack-developers for guidance! Protect plugin:
If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack. |
Are you an Automattician? Please test your changes on all WordPress.com environments to help mitigate accidental explosions.
Interested in more tips and information?
|
798bd3c
to
672be6f
Compare
672be6f
to
7cd0e22
Compare
5203dab
to
3cc7ee0
Compare
6b2f6a2
to
748eeb1
Compare
160323a
to
a294482
Compare
a294482
to
06dfbb4
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
Proposed changes:
Other information:
Jetpack product discussion
https://github.com/Automattic/jetpack-scan-team/issues/1382
Does this pull request change what data or activity we track or use?
No
Testing instructions:
Note: using your local development environment to test this PR will allow you to view the React Query developer tools via a floating icon on the bottom right of the screen.
Monitor the network tab for the duration of your testing. Ensure no async requests are triggered on page load (data comes from initial state), request polling occurs for in-progress scans and fixers, and related data is refreshed after actions are made (i.e. refresh scan status after ignoring a threat).
?foo=<script>
in the URL is blocked when automatic rules are enabled).